feat: [IOCOM-2100] Common FIMS start API #6740
Open
+1,494
−409
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR Title Validation for conventional commit type✅ All good! PR title follows the conventional commit type. |
Jira Pull Request LinkThis Pull Request refers to Jira issues: |
# Conflicts: # ts/features/services/details/screens/ServiceDetailsScreen.tsx
Vangaorth
requested review from
dmnplb,
ChrisMattew,
gispada,
freddi301 and
a team
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short description
This PR centralise the starting of the FIMS authentication flow.
List of changes proposed in this pull request
There are now three hooks that allow to properly start the FIMS flow from a react-native component
useFIMSFromServiceId: when you know the service Id ahead of time and the service details are already loaded into memory (e.g, from message and service details)useFIMSAuthenticationFlow: when you do not know the service Id ahead of time but will have it upon authentication flow invokation (e.g., a bonus of IdPay)useFIMSRemoteServiceConfiguration: when the service data are stored in the CDN and you know the configuration id associated with such configuration (e.g., from the wallet driving license). Be aware that calling this hook with an invalid configuration Id will not start the authentication flow later onAll these hooks return an authentication callback that starts the FIMS authentication flow upon invocation.
How to test
Using the io-dev-api-server, check that all existing FIMS authentication flows are working as expected.